Search This CD Index Contact Us
Home > Administration > Networking > AMIS Analog Networking > AMIS Analog Networking Administration > Administering AMIS Remote Machines or Telephone Numbers > Machine Profile Screen for a Remote Machine, Page 2
| Machine Profile Screen for a Remote Machine, Page 2
> Table: Field Definitions: Remote Machine Profile Screen, Page 2
> Field | Valid Input | Description
> --- | --- | ---
> Dial String | The valid input depends on the machine type. See the Description for an explanation of the valid input for each machine type. | Enter the telephone number of the remote machine. The local machine uses the dial string to contact and send messages to the remote machine. Valid entries vary for different network connection types as described in the following list: amisac and calld (optional). For amisac machines (AMIS casual or two-step addressing), the dial string is optional. If used, it can be from 0 to 24 characters and consists of any numbers the system should add to the number subscribers dial to reach a specific address. The dial string plus the extension must be less than or equal to 29 characters. For a range of local numbers, the dial string might be "9" (or whatever trunk-access code or dial-access code is assigned to reach the public network). For example, if the extension length is "7" and a subscriber specifies a valid 7-digit address (such as 555-6000), the local system dials 95556000 to reach the remote machine. For a range of long-distance numbers, the dial string is normally 91 in the United States (the trunk-access code or dial-access code, followed by 1). For example, if the extension length is 10 and a subscriber specifies a valid 10-digit address (such as 201-555-6000), the local system dials 912015556000 to reach the remote machine. amisap (required). For amisap machines (AMIS preadministered or one-step addressing), the dial string is required. It can be up to 65 characters long and typically consists of the trunk-access code or dial-access code needed to reach the public or private network, followed by a pause interval, and then followed by the complete telephone number of the remote machine. Note: You can instruct the local system to pause for a specified length of time by entering "P" (including quotes) in the dial string. A single "P" causes the system to pause approximately 1.5 seconds; a "P" followed by a digit from 1 to 9 causes the system to wait the specified amount of time. For example, if the dial string is 9"P2"5556000, the local system dials 9, waits about 3 seconds, and then dials 5556000.
> Callback Number | From 1 to 5, must reference a completed callback number, except default callback number 1. | Select the number associated with the preadministered callback numbers that are listed below this field. The Callback Number is the number that other systems will use to contact this machine. These callback numbers are administered on the System-Parameters Analog-Network screen. For machine type "calld," this field is ignored.
> Message Transmission Schedule/Start and End | From 00:00 to 23:59 | The message transmission schedule allows you to set time intervals for network communications. The INTUITY system sends recorded messages only to the remote machine during the time intervals or send times you specify. Specify Start and End times by using a 24-hour or military time clock that starts at 00:00 and ends at 23:59. For example, if you want the start time to be 11:00 p.m., enter 23:00 in the Start Time field. You can specify up to three cycles for each remote system. Cycles can be assigned to avoid toll facilities or periods of heavy traffic if desired. The total time of the cycles can neither exceed 24 hours nor overlap each other. A cycle can span across midnight. Note: The times specified must be equal to or a subset of the outcalling transmission times administered on the System Parameters Outcalling screen; otherwise, the AMIS or message delivery messages will never be sent. For example, if you schedule AMIS and message delivery messages to be sent any time during a 24-hour period (from 00:00 to 23:59), but outcalling periods are scheduled only from 07:00 to 18:00, AMIS and message delivery messages are sent between the hours of 7:00 a.m. and 6:00 p.m. If all the outcalling ports are busy, the system retries in one minute. If an outcalling port is available, but for some reason the system cannot deliver the message, the system uses the value entered in the `Rescheduling Increments For Unsuccessful Message Delivery` field on the System Parameters Features screen.
> Send to Non-Administered Recipients? | y= yes n = no | Enter y or n depending on whether you want to allow subscribers to send messages to nonadministered recipients. Set to y only after testing the network end to end during initial administration. If you want to set this field to Y, the`Updates In` field must also be set to y on the local Machine Profile screen. When a subscriber addresses a message to a remote extension that does not map to an address known by the local system, the local system adds this potential subscriber to the database and then sends the message to every remote system in the network for which the address is valid. If a valid remote recipient cannot be found, the subscriber record is deleted eventually by one of the system audits, and the local system changes the status of the message from undelivered to undeliverable in the sender's outgoing voice mailbox. For AMIS one-step systems and message delivery, if this field is set to n, subscribers can only send messages to administered remote subscribers. If a subscriber enters a valid extension or telephone number, but one that is not administered, the subscriber is notified that the entry is invalid. For AMIS two-step systems, this field must be set to y because all remote subscribers on these systems are nonadministered. Setting the field to n prevents all AMIS casual messages from being delivered on INTUITY systems. Note: Permitting subscribers to send messages to nonadministered recipients could have a significant impact on the network, thus causing extra or unnecessary calls to other systems and loading the local subscriber database with unneeded records. If the network is kept up to date, change the field to n to reduce the system load. Often, messages to nonadministered recipients simply indicate a misdialed number.
Top of page

| Search This CD Index Contact Us
| © 2002-2007 Avaya Inc. All rights reserved.